Modeling software deployment in HCL Launch includes configuring components and component processes and adding those components to applications. Then, you use processes to deploy the components to environments.
A resource is a logical deployment target that typically resolves to an agent and a user-defined construct that is based on the architectural model of HCL Launch.
You can create, delete, and modify the contents of the resource tree.
Components represent deployable items along with user-defined processes that operate on them, usually by deploying them.
Resources associate agents with components and, after they are mapped to an application environment, provide deployment targets.
Resource groups organize resources into logical groupings.
Agent-type and agent pool-type resources represent the computers where components are deployed.
Component-type resources represent the components that are deployed to target environments.
You can find agents that are not associated with a resource and add them to a resource group.
Resource tree structures in the Resources Tree page can be configured by moving and copying the resources using the drag and drop feature.
Resources can be deleted by using the Delete action on the Resources page.
You can compare the contents of a resource group to another group or a resource template and then apply changes to the group or template.
You can add the contents of a resource template to the top-level resource group.
You can add the structure from a resource template to a new group within an existing resource group.
Use the WebSphere® Application Server - Deploy plug-in to import information about an IBM® WebSphere Application Server system into a collection of resources. Typically, importing information by using the plug-in takes less time than manually creating resources to match the IBM WebSphere Application Server.
With the WebSphere® Portal plug-in, you can discover resources for a portal cell and use plug-in steps to deploy artifacts.
You can define default user impersonation credentials for a resource.
A resource template is a model for a group of resources. The template contains a hierarchy of resources, groups, and agent prototypes that is a starting point for creating new resources.
An agent is a lightweight process that runs on a deployment-target host and communicates with the HCL Launch server.
Agent relays coordinate communication between agents and the HCL Launch server. Agent relays improve the performance of communication between the server and agents. Relays also allow agents to communicate through firewalls.
Applications are responsible for bringing together all the components that must be deployed together.
An environment is a user-defined collection of resources that hosts an application.
With an application template, you can save and reuse a collection of resources, environments, processes, and tagged components or component templates to create a standardized application.
Application processes, like component processes, are created with the process editor. You use application processes to deploy or to roll back components.
An application blueprint maps application components to a resource template. When you create an environment or provision one from the cloud, you can use the blueprint as a model.
A snapshot is a collection of specific versions of components and processes. Typically, a snapshot represents a set of component versions that are known to work together. In most cases, snapshots include all of the components in an application.
A manual application task interrupts an application process until manual intervention is done. To create a manual task, add a manual step to an application process and select a notification template.
You can add approval requirements to deployments. Deployments with approvals cannot be completed until all approvers respond. Approvers can respond to requests on the Work Items tab, or by email.
You use different inventories to track installed components and properties in HCL Launch elements.
Processes are automated tasks that run on agents.
Create and apply statuses to track component inventory states or to track component versions in environments and resources.
Properties are variables that store information about many different elements, including components, environments, processes, and applications. You can also set global properties for the system.
A tag is a user-defined, shared, short label that you use to classify, view, and conduct operations on objects such as applications, components, agents, and resources.
Using the webhooks, you can send text-based responses to users in messaging platform such as MS Teams and Slack when a specific event occurs during deployment process.
Allows HCL Launch to retrieve credentials of individual servers from the Vault and authenticates a plug-in step in the deployment process.